feat(helm): add licenseProxy values for corporate HTTP proxy support#5
Merged
Conversation
Add a licenseProxy section to values.yaml (host, port, user, password) that automatically generates a ConfigMap containing license.config and mounts it into vtom-server, vtom-apiserver, itc, and itm. This allows the Absyss Java license client to reach license-ctrl.customer.absyss.com through a corporate HTTP proxy without any manual Kubernetes object creation. When licenseProxy.host is empty (default), no ConfigMap is created and no volume mount is added — existing deployments are unaffected. Also adds the missing license.config mount to vtom-server (deployment-server.yaml), which previously had no proxy support even when configured manually. The values-client-template.yaml is updated with the new commented section so operators are aware of the option during deployment.
…echanism does not support license.config
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
licenseProxysection tovalues.yaml(host, port, user, password) that automatically generates a ConfigMap containinglicense.configand mounts it intovtom-server,vtom-apiserver,itc, anditmlicense-ctrl.customer.absyss.comthrough a corporate HTTP proxy without any manual Kubernetes object creationlicenseProxy.hostis empty (default), no ConfigMap is created and no volume mount is added — existing deployments are unaffectedlicense.configmount onvtom-server(deployment-server.yaml), which had no proxy support even when configured manuallyvalues-client-template.yamlwith the new commented section so operators are aware of the optionUsage
Test plan
helm templatewithlicenseProxy.hostset renders the ConfigMap and volume mounts in all 4 deploymentshelm templatewithlicenseProxy.hostempty renders no ConfigMap and no volume mounts